-
Notifications
You must be signed in to change notification settings - Fork 106
Handle bad xmlrpc data with BadRequest #1244
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
helps ignore spam/pentest requests
I have observed requests like this and similar over the last few months. There are a couple other types that provoke tracebacks like this. The requested URL as stored in
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please add a changelog entry
I have added the change log entry and merged it myself because I want this on master before creating a branch to work on the other types of spam/pen test requests I have been seeing. |
@dataflake there is another. A call like blah.jpg/@@images (ie missing the rest of the path). Then you get
Which I think should also be a BadRequest. |
If you have time for it please do. |
helps ignore spam/pentest requests